release: prepare the reviewed 0.1.0 first-public-release unlock - #5

Summary

Preparatory review artifact for OpenCoven#41 (first public release, version 0.1.0). It completes work-plan items 1-5 on a branch stacked on security/first-release-review-40:

• Authorization record (docs/release/sdk-0.1.0-release-authorization-record.md): names the exact fixed-group version 0.1.0, the four-package set with @opencoven/dev-cli deferred ([SDK 0.1.0][P0] Resolve CLI scope and implement native trust boundaries OpenCoven/sdk#37/build: defer private CLI from SDK 0.1 release OpenCoven/sdk#57), the supported Node/OS/architecture matrix, launch criteria, and a rollback-owner proposal. The decision itself is marked pending fresh maintainer authorization.
• Versioning: the canonical pnpm release:version run consumed the two pending pre-release changesets; the managed-native custody and browser-safe subpath summaries are folded into the ## 0.1.0 changelog entries of @opencoven/sdk-core and @opencoven/cave-client. Versions stay pinned at exactly 0.1.0 with exact workspace:0.1.0 internal ranges; no version bump is pending.
• Publication locks opened as reviewed PR changes: release.config.json sets publishingEnabled to true and the four release manifests become publishable. The independent deployment lock (protected npm-release environment approval), OIDC id-token/attestations permissions, the prepublishOnly authorization gate, and the no-token-fallback rule are preserved unchanged. Tests that pinned the closed state now pin the reviewed open state (both sides of the privacy lock, artifact-before-npm ordering, token-fallback rejection). Nothing is activated: no tag, no publish, no release-workflow dispatch.
• Rehearsal runbook (docs/workflows/first-release-rehearsal-runbook.md): the no-publish operator procedure — annotated sdk-v0.1.0 tag at the reviewed commit, release-workflow verify mode, artifact retention, registry-unchanged proof, digest comparison with the reviewed candidate — plus the authorization-gated continuation (issue steps 5-7: one-time bootstrap publish, trusted publishing, registry/provenance validation) with per-step authorization stops and the master authorization sentence. Reviewed-candidate digests are recorded and confirmed reproducible at this head.

Authorization status: pending fresh maintainer authorization. Nothing external has been tagged, published, unlocked, or dispatched; the OpenCoven#38/F-1 platform-record gap (Chat schema-v2 records on darwin-arm64 / linux-x64 / win32-x64) remains unresolved until a maintainer resolves or formally waives it.

Assignee: @CompleteDotTech
Advances OpenCoven#41 (gates OpenCoven#42/OpenCoven#44 and OpenCoven#31 closure)

Stacked on fork PR #1 (security/first-release-review-40): merge #1 first. After #1 merges upstream, rebase this branch onto origin/main and flip this PR base to main — the upstream compare then shows only the delta.

Stacked upstream compare (delta view for review): https://github.com/OpenCoven/sdk/compare/main...CompleteDotTech:sdk:release/sdk-0.1.0-unlock-41?expand=1

Validation

• Targeted tests cover the changed behavior: tests/release-readiness.spec.ts, tests/package-manifests.spec.ts, and tests/release-policy.spec.ts updated with the lock change (58 test files / 1215 tests pass locally, +2 net over the parent head).
• corepack pnpm@10.34.0 verify passes (exit 0 on head d792b4a: typecheck, clean public dist, build + tests, verify:contracts, verify:package, verify:release, coverage, multi-seed stress, lint) and git diff --check is clean.
• No Changeset added, deliberately: the release-unlock change consumes the pending pre-release changesets into the ## 0.1.0 entries instead, so no version bump is pending (repository-maintenance changes need no changeset per .changeset/README.md).
• Documentation updated: README.md and RELEASING.md release-status language, authorization record, rehearsal runbook.
• No credentials, private endpoints, or sensitive error causes are included. No tag, no registry mutation, no release-workflow dispatch; local dry-runs wrote only to throwaway temp directories.

Release impact

Opens the repository publication lock for the 0.1.0 first public release as a reviewable change while preserving the fail-closed two-key design: activation additionally requires the protected npm-release environment approval, the maintainer-authorized sdk-v0.1.0 tag, and a release-workflow dispatch from main. Compatibility: none (no code or API change; versions unchanged at 0.1.0). Migration: none.